UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).


Overview

Finding ID Version Rule ID IA Controls Severity
V-252157 MD4X-00-002800 SV-252157r813853_rule Medium
Description
To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system. Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following: (i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and (ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals using shared accounts, for detailed accountability of individual activity.
STIG Date
MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide 2022-09-12

Details

Check Text ( C-55613r813851_chk )
For each database in the system, run the following command:

use database
db.getUsers()

Ensure each user identified is a member of an appropriate organization that can access the database.

Alternatively, if LDAP/AD is being used for authentication/authorization, the mongoldap tool can be used to verify user account access.

If a user is found not be a member of an appropriate organization that can access the database, this is a finding.

Verify that the MongoDB configuration file (default location: /etc/mongod.conf) contains the following:

security:
authorization: enabled

If this parameter is not present, this is a finding.
Fix Text (F-55563r813852_fix)
For any user not a member of an appropriate organization and has access to a database in the system, run the following command:

use database
db.dropUser(%username%, {w: "majority", wtimeout: 5000})

If the %MongoDB configuration file% (default location: /etc/mongod.conf) does not contain

security:
authorization: enabled

Edit the %MongoDB configuration file%, add these parameters, stop/start (restart) any mongod or mongos process using this %MongoDB configuration file%.